Use IConfigurationBuilder, IConfiguration, and Typed Configuration to centralize the way we manage CLI behaviors #49761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft that's building on the work that the test team started with
dotnet.config
- if we can get the majority of the CLI working on a shared IConfiguration-based configuration layer/abstraction, then we can separately evolve the things that feed in to that configuration.This is a mostly-vibe-coded draft of that idea - now I want to see what CI thinks.